Add support for multiple Asgardeo Provider instances via optional instanceID #325
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose
This pull request introduces support for multiple authentication contexts ("multi-auth context") in the Asgardeo React SDK by adding an
instanceIdparameter throughout the authentication client and provider. This enables applications to manage multiple independent authentication sessions within the same app instance. The most important changes are grouped below:Multi-auth context support:
instanceIdproperty to theAsgardeoReactConfiginterface to allow configuration of multiple authentication contexts.AsgardeoReactClientclass to accept aninstanceIdin its constructor, store it, and provide agetInstanceId()method. TheAuthAPIis now initialized with theinstanceIdas well.AuthAPIclass to accept and store aninstanceId, pass it to the underlying SPA client, and expose agetInstanceId()method. [1] [2]AsgardeoProviderReact component to accept an optionalinstanceIdprop (defaulting to 0), and to instantiate theAsgardeoReactClientwith this value, ensuring correct context isolation.Related Issues
Related PRs
Checklist
Security checks